Agent step troubleshooting

Raw event data or timestamps

Symptom: The Agent step's output contains text like event: message and timestamp fields instead of just the agent's response.

Cause: This is the Agent step's default output format — it is not an error.

Fix: Add a Data Process step after the Agent step to extract just the message. Refer to Data Process step.

Copying a connection component to another account

Symptom: An Agent connection component copied from one account to another fails when the process runs.

Cause: Agent connection components are tied to the account in which they were created. A copied component still references the original account in its component URL.

Fix: Don't copy Agent connection components between accounts. Delete the copied component and reconfigure the Agent step in the new account to let the system recreate it with the correct account information.

Agent version

Symptom: You deployed a new version (for example, v2) of an agent in Agent Garden, but the Agent step configuration still shows v1, or behaves unexpectedly.

Cause: Existing Agent step configurations remain unchanged by design, to protect stability. The input and output schemas only update when you explicitly sync, and the version selector stays on v1 until you manually change it. Because multiple packaged versions can share the same deployment_id, the step may already be executing the latest deployed version even while the UI still displays the older one.

Fix: Select Sync with Agent Studio in the Agent step configuration to pick up the current schema. Manually update the version selector if you want the UI to reflect the new version. Confirm behavior with a test run after syncing, since schema mismatches from an out-of-date configuration can cause execution failures.

Structured agent profile

Symptom: A structured-mode agent doesn't show a profile when configuring the Agent step.

Cause: The agent was created before the November 8 platform release, and older structured agents don't automatically expose a profile to the Agent step.

Fix: Modify and re-sync the agent in Agentstudio. Newly created structured agents generate profiles directly without this step.

Process times out

Symptom: A process running an Agent step waits indefinitely, or fails after an unpredictable delay.

Fix: Open the configuration component for the Agent step in the Component Explorer and set connection and read timeouts under Advanced Configuration (Timeouts), so the process fails fast instead of waiting indefinitely.

Local runtime connectivity

Symptom: An Agent step fails to connect when running on a local Atom or Molecule.

Cause: Local runtimes need explicit network access to Agent Tower.

Fix: Add the required IP addresses to your allowlist. Refer to Hostnames and IP address for the Boomi Enterprise Platform.

Agent step can't be edited

Symptom: You need to change the Platform Username, Platform API Token, or other connection details but the fields don't behave as expected, or editing them breaks the step.

Cause: These fields are populated automatically from the account used to create the Agent step and aren't meant to be edited manually. Modifying them can disrupt the connection between the Agent step and the agent.

Fix: Avoid editing Platform Username and Platform API Token directly. If a connection component is broken (for example, after a bad copy between accounts), delete it and reconfigure the step instead of trying to fix the fields in place.